deps: bump reth to v2.4.1 and op-reth to v2.4.1 - #569
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR upgrades the workspace’s reth/op-reth stack to the op-reth/v2.4.1-aligned reth rev, along with associated dependency bumps (revm, alloy), and updates op-rbuilder code to compile against the new APIs while keeping reth’s new default JIT/GMP features disabled.
Changes:
- Bump reth to the op-reth-aligned rev and op-reth crates to
op-reth/v2.4.1; bump revm to41.xand alloy/alloy-evm to newer2.x/0.37.x. - Adapt to upstream API shape changes (new blobstore method; new payload delta fields; new executed-block field).
- Fix CLI argument-name collision via explicit clap arg
id; adjust benchmark chain spec preset and chain id.
Reviewed changes
Copilot reviewed 7 out of 8 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| crates/op-rbuilder/src/pool/delegate.rs | Adds delegation for newly introduced blobstore API (has_blobs_for_versioned_hashes). |
| crates/op-rbuilder/src/flashtestations/args.rs | Adds explicit clap arg id to avoid collision with newly flattened upstream args. |
| crates/op-rbuilder/src/builder/wspub.rs | Updates golden-wire payload construction to include new post_exec_tx field. |
| crates/op-rbuilder/src/builder/fanout.rs | Updates tests’ payload delta construction to include new post_exec_tx field. |
| crates/op-rbuilder/src/builder/assembly.rs | Populates new upstream struct fields (changed_paths, post_exec_tx) with None. |
| crates/op-rbuilder/benches/bench_build_candidate.rs | Switches benchmark chain spec preset and chain id to Optimism mainnet values. |
| Cargo.toml | Re-pins reth to a specific rev with default features disabled; bumps workspace dependency versions. |
| Cargo.lock | Updates resolved dependency graph to match the new versions/pins. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- reth: tag v2.3.0 -> rev f2eecc65, matching the reth pin of the op-reth/v2.4.1 tag (rev is a couple commits past the v2.4.1 tag; using the same declaration keeps cargo resolving a single copy of every reth crate). Documented in Cargo.toml for future bumps. - op-reth: op-reth/v2.4.0 -> op-reth/v2.4.1 (workspace deps + crates-io patches) - alloy 2.0.5 -> 2.1.1, alloy-evm 0.36 -> 0.37, revm 40 -> 41, reth-primitives-traits 0.4.1 -> 0.5.0 - opt out of reth's new default jit (revmc/LLVM) and gmp features to avoid native LLVM/GMP build deps; keeps the v2.3.0 default feature set (op-reth's own binary ships without jit/gmp as well) - delegate new TransactionPool::has_blobs_for_versioned_hashes on Flashpool - BuiltPayloadExecutedBlock: changed_paths = None (same as upstream op-reth payload builder) - flashblock deltas: post_exec_tx = None; the builder does not produce SDM post-exec transactions (field is skip-serialized when None so the wire format is unchanged) - flashtestations: explicit clap id for --flashtestations.debug; reth v2.4.x's flattened JitArgs also derives an argument id "debug"
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 7 out of 8 changed files in this pull request and generated no new comments.
Suppressed comments (1)
Cargo.toml:123
- The PR description says alloy is being bumped to 2.2.0, but the workspace dependency entries here are set to 2.1.1; Cargo.lock is already resolving alloy 2.2.0, so this mismatch makes the upgrade intent unclear. Either update these versions to 2.2.0 (recommended for clarity/reproducibility) or adjust the PR description to match what is pinned.
alloy-consensus = { version = "2.1.1", features = ["kzg"] }
akundaz
approved these changes
Jul 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
reth v2.3.0 -> rev f2eecc65 (same as op-reth/v2.4.1, ~reth 2.4.1)
op-reth v2.4.0 -> v2.4.1
alloy 2.0.5 -> 2.2.0
alloy-evm 0.36 -> 0.37
revm 40 -> 41
reth-primitives-traits 0.4.1 -> 0.5.0
Opted out of reth new default jit/gmp features (no need for LLVM/GMP native deps for non l1 evm)